Support of Microsoft® Virtual Server with NetApp FCP and iSCSI Storage Systems

 

Last Updated: 21 September 2007

Original Date: 21 September 2007

 

CONFIDENTIAL Restricted to NetApp employees & channel partners under NDA copyright © 2007 Network Appliance Inc. All rights reserved.

Regulatory Compliance Verification

 

Date of Revision

Summary of changes

 21 September 2007

Initial version

 

1.       Summary

2.       What's New?

3.       System Requirements

4.       Product Information

5.       Regulatory Compliance

6.       Warranty and Service

7.       Additional Information


 

1.   Summary

 

This product bulletin announces support of Microsoft Virtual Server 2005 R2 SP1 with Windows® Server 2003 and NetApp FCP and iSCSI storage systems.

 

Microsoft Virtual Server is a virtualization platform supported by Microsoft with Windows Server 2003 and numerous x86 operating systems in guest environments to enable server consolidation and rehosting of legacy operating systems and their applications, and to support disaster recovery plans that require application portability across server platforms. 

 

For more information about Microsoft Virtual Server, see http://www.microsoft.com/windowsserversystem/virtualserver/. 

 

NetApp support of Microsoft Virtual Server means that FCP and iSCSI storage systems are supported with host and I/O stack configurations outlined in the NetApp Interoperability Matrix:  http://now.netapp.com/NOW/products/interoperability/. 

 

Additionally, SnapDrive® 5.0 for Windows is supported in iSCSI configurations with a NetApp supported Microsoft software iSCSI initiator from within a Windows guest operating system. Support of Microsoft Virtual Server with SnapDrive in FCP and iSCSI configurations running from the host operating system is targeted for future SnapDrive releases.

 

 

2.   What’s New

 

This product bulletin is an overview of   current NetApp support of Microsoft Virtual Server 2005 R2 SP1 with FCP or iSCSI storage systems and the ongoing support strategy for SAN connectivity with Microsoft Virtual Server 2005.

 

NetApp supports Virtual Server 2005 as it does any other host application and does not require additional qualification beyond that required to support FCP and iSCSI with Windows Server 2003. However, in certain instances (defined later in this document), Windows virtual machine registry setting changes are required to ensure proper operation.

 

Microsoft Virtual Server 2005 is a service that runs on top of a host operating system. Therefore Microsoft Virtual Server 2005 relies on the underlying host operating system to provide the FCP and iSCSI drivers for connecting to a SAN. This is different from VMware ESX Server, which is its own operating system with FCP and iSCSI initiator drivers and requires specific qualification for support with NetApp storage systems.

 

3.   System Requirements

 

Support Requirements

NetApp supports Virtual Server 2005 with FCP and iSCSI storage systems in two primary configurations:

 

·         A NetApp supported software iSCSI initiator running from within a Virtual Server 2005 guest operating system. This configuration is supported with SnapDrive 5.0 for Windows.

·         A NetApp supported Windows Server 2003 FCP or iSCSI initiator running from the host operating system, on top of which Microsoft Virtual Server runs. These configurations are not currently supported with SnapDrive for Windows; support is targeted for future SnapDrive releases.

 

The following table lists the hardware and software platform requirements for support of Microsoft Virtual Server 2005 with FCP and iSCSI storage systems.

 

Microsoft Virtual Server versions

Microsoft Virtual Server 2005 R2 SP1

Host operating systems

Microsoft Windows Server 2003 SP1 and  SP2, Microsoft Windows Server 2003 R2

Platform CPU architecture

x86, x64 (AMD64, EM64T)

Host clustering

Microsoft Cluster Server clustering of host operating system

Guest operating systems

All guest operating systems supported by Microsoft Virtual Server

See the Microsoft Web site for the latest information: http://www.microsoft.com/technet/virtualserver/software/faq.mspx.

 

·         Use of Virtual Server 2005 requires a NetApp supported Windows Server 2003 initiator and host configuration.

 

See the NetApp Interoperability Matrix for the latest Windows Server 2003 supported configurations: http://now.netapp.com/NOW/products/interoperability/.

 

·         Windows guest operating systems using virtual SCSI disks require registry- setting updates.

 

Disk Class Timeout in a Windows Guest operating system with virtual disks must  be changed to 60 seconds (Windows Registry setting HKLM\SYSTEM\CurrentControlSet\Services\disk). See the latest iSCSI Windows Host Utilities for Native OS Release Notes here or FCP Windows Host Utilities for Native OS Release Notes here for additional information and instructions on how to change the registry setting.

·         SnapDrive for Windows 5.0 is supported with a NetApp supported Microsoft software iSCSI initiator from within a Windows guest operating system.

SnapDrive for Windows is not currently supported with FCP or iSCSI running from the host operating system; this support is targeted for future SnapDrive releases.

6.   Product Information

 

There is no new product offering for support of Microsoft Virtual Server 2005.

 

Software Subscription Plans

 

Not applicable.

 

Upgrades

 

Not applicable with Host Utilities. Periodic refreshes to Host Utilities will occur over time. For the latest support information, see the NetApp Interoperability Matrix: http://now.netapp.com/NOW/products/interoperability/.

                                                                                                    

Quoting

 

There is no NetApp license, part number, or price for support of Microsoft Virtual Server 2005. NetApp support is available through existing SupportEdge contracts and processes.

 

Product Availability

 

NetApp continues to offer the Data ONTAP® iSCSI license through the iSCSI Enablement Program free of charge to customers who meet certain requirements. Details about the free iSCSI license enablement program are available here.

                             

The NetApp iSCSI Host Utilities are available free of charge for download from the NOW™ (NetApp on the Web) site, with a valid NOW login ID.

 

Microsoft Virtual Server 2005 R2 SP1 software is available free of charge from Microsoft at http://www.microsoft.com/technet/prodtechnol/eval/virtualserver/default.mspx.

                             

 

7.   Regulatory Compliance

 

Products need to be validated against the Netapp Regulatory Compliance Country List prior to order submission. The list is available at PartnerCenter Compliance Information. This is required to ensure that products are being sold only in the countries in which NetApp has received regulatory compliance certification. For further information of this requirement, please see the Regulatory Compliance Verification Product Bulletin.

 

 

8.   Warranty and Service

 

TBD

 

 

9.   Additional Information

 

For the latest NetApp support information, see the NetApp Interoperability Matrix:  http://now.netapp.com/NOW/products/interoperability/.

 

Additional information on Microsoft Virtual Server 2005 is available on the Microsoft web site:

·         Virtual Server 2005 R2 SP1 Product Overview

·         Virtual Server 2005 Product Documentation

·         Microsoft Virtual Server TechCenter

 

Contact Information: Please contact your Network Appliance sales or channel partner representative with questions about this product bulletin.

 

© 2007 Network Appliance, Inc. All rights reserved. Specifications subject to change without notice. NetApp, the Network Appliance logo, Data ONTAP, and SnapDrive are registered trademarks and Network Appliance and NOW are trademarks of Network Appliance, Inc. in the U.S. and other countries. Microsoft and Windows are registered trademarks of Microsoft Corporation. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such.